Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

2140

reference
76-tree-1
name
2140
tree-preservation-order

undefined

76-tpo-1
uprn
address-text
point
POINT (-1.006351 50.891831)
geometry
MULTIPOLYGON (((-1.006294 50.891825,-1.006297 50.891836,-1.006305 50.891846,-1.006317 50.891854,-1.006333 50.891859,-1.006350 50.891861,-1.006368 50.891860,-1.006384 50.891855,-1.006397 50.891847,-1.006405 50.891837,-1.006408 50.891826,-1.006405 50.891815,-1.006397 50.891805,-1.006385 50.891797,-1.006369 50.891791,-1.006352 50.891789,-1.006334 50.891791,-1.006318 50.891796,-1.006305 50.891804,-1.006297 50.891814,-1.006294 50.891825)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL